bug: Identifiers can't be parsed cross module boundaries#1560
Closed
DarkPurple141 wants to merge 1 commit into
Closed
bug: Identifiers can't be parsed cross module boundaries#1560DarkPurple141 wants to merge 1 commit into
DarkPurple141 wants to merge 1 commit into
Conversation
DarkPurple141
commented
Feb 7, 2023
| it("import-exposed", assertValidSchema("import-exposed", "MyObject")); | ||
| it("import-internal", assertValidSchema("import-internal", "MyObject", "basic")); | ||
| it("import-anonymous", assertValidSchema("import-anonymous", "MyObject")); | ||
| it.only("import-identifier", assertValidSchema("import-identifier", "MyObject")); |
Member
|
Thanks for the repro. This will Haley confirm the fix later. |
Collaborator
|
Hey @DarkPurple141 is this still a problem? |
|
I merged in Seems to work now The updated branch: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a minimal reproduction of existing behavior around the
NodeParserthrowing anUnknownNodeErrorfor valid in scope identifiers.eg.
Error:
My expectation of is that this would be able to be parsed - as this kind of type inference via an identifier is a common use case.